David/GitHub action update cdn#389
Conversation
ayjayt
left a comment
ayjayt
left a comment
There was a problem hiding this comment.
non-zero or zero exit, it matters:
if sys.exit(0), the action is marked as success.
if sys.exit(1), the action is marked as a failure.
When should it marked as failure? When as success?
Should be marked as failure when the user needs to be notified as something.
Careful with the prints. It would be nice if w/ action success/failure status, the subtitle was whatever link the user had to follow. This is what github pages does when a new pages is published.
Can this also automatically update the CHANGELOG is a second commit?
ayjayt
left a comment
ayjayt
left a comment
There was a problem hiding this comment.
ok i just dont understand why you are not printing more to stderr.
stdout would be like if the user is expecting some out. if something unexpected happens, we print it to stderr. i think we can print to stderr and still return 0 from program if its unexpected but ok.
but not a big deal, i will approve.
|
@davidangarita1 please merge this with main and rerun |
|
@davidangarita1 once it is accepted remind me and we will trigger it automatically. |
| tag-check: ${{ env.IS_TAG_PUSH == 'true' && env.TAG || '' }} | ||
| summarize-news: ${{ env.IS_PR_TO_DEFAULT == 'true' && 'origin.txt updated.txt' || '' }} | ||
| - name: Check .editorconfig exists | ||
| run: | |
There was a problem hiding this comment.
i'm gonna change some things
|
This is approved but we need to get some other stuff in first. |
|
nevermind on approval, there are ruff errors @davidangarita1 |
3 participants
automatic update of plotly.js